home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
ftp.cs.arizona.edu
/
ftp.cs.arizona.edu.tar
/
ftp.cs.arizona.edu
/
icon
/
newsgrp
/
group97b.txt
/
000125_icon-group-sender _Mon Nov 24 08:30:31 1997.msg
< prev
next >
Wrap
Internet Message Format
|
2000-09-20
|
1KB
Return-Path: <icon-group-sender>
Received: from kingfisher.CS.Arizona.EDU (kingfisher.CS.Arizona.EDU [192.12.69.239])
by baskerville.CS.Arizona.EDU (8.8.7/8.8.7) with SMTP id IAA20012
for <icon-group-addresses@baskerville.CS.Arizona.EDU>; Mon, 24 Nov 1997 08:30:30 -0700 (MST)
Received: by kingfisher.CS.Arizona.EDU (5.65v4.0/1.1.8.2/08Nov94-0446PM)
id AA06626; Mon, 24 Nov 1997 08:30:30 -0700
To: icon-group@optima.CS.Arizona.EDU
Date: 22 Nov 1997 01:03:35 -0500
From: rdd@access2.digex.net (R. D. Davis)
Message-Id: <655sjn$ebr@access2.digex.net>
Organization: Society for the Obsolescence of Obsolescence
Sender: icon-group-request@optima.CS.Arizona.EDU
Subject: File locking in Icon
Errors-To: icon-group-errors@optima.CS.Arizona.EDU
Status: RO
While looking over the procedure files for Icon, and the documentation
available via the Univ. of Arizona's Icon WWW page, I haven't seen
anything pertaining to file locking thus far. (yes, I know, I should
have ordered the Icon programming book, which I plan to do).
Am I going to need to implement file locking using C code for my
programs, to be called by Icon programs, or am I overlooking something?
--
R.D. Davis http://www.access.digex.net/~rdd
rdd@access.digex.net Computer preservationist. Many types of
...!uunet!mystica!rdd unwanted older computer systems disassembled,
Office telephone: 1-410-744-4900 removed for free (locally) and preserved.